Feat/actions crawler #1
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey, We're running a downstream iteration of this at https://github.com/etclabscore/discv4-dns-lists, and have the crawler running on the Github Actions CI there. This frees up a devops task and makes the provenance of the lists transparent.
Here's a start at adding the same functionality here if you're interested.
The config currently uses Actions'
schedule: cron
config with what I thought is a sufficient time span. There are other ways to handle this, but this seemed the simplest to me.TODO
Repo Secrets
The Action config depends on a few Secrets being set at the Github repo level.
CLOUDFLARE_API_TOKEN
ETH_DNS_CLOUDFLARE_ZONEID
(This isn't necessary if you can get get thedevp2p to-xxx
to work without it.... I couldn't.)ETH_DNS_DISCV4_KEY
: The full content of the signing key file, eg.cat key.json | pbcopy
or whatever.ETH_DNS_DISCV4_KEYPASS
: The key's password.GITHUB_USER_PERSONAL_ACCESS_TOKEN
(PAT). If you can get thegit push
to work without explicit user authentication (see comment below) then you won't need this.